Continuous Release

CDN link

• https://raw.esm.sh/pr/p5@4f666c3/lib/p5.min.js

Published Packages

• https://pkg.pr.new/p5@4f666c3

Commit hash: 4f666c3

This is an automated message.

vitest.config.js only applies the SwiftShader software-rendering Chromium flags when process.env.CI is set:

provider: playwright({
              capabilities: process.env.CI
                ? {
                    'goog:chromeOptions': {
                      args: [
                        '--no-sandbox',
                        '--headless=new',
                        '--enable-unsafe-webgpu',
                        '--use-vulkan=swiftshader',
                        '--use-webgpu-adapter=swiftshader',
                        '--use-angle=vulkan'
                      ]
                    }
                  }
                : undefined
            }),

So CI renders text through SwiftShader while a local run uses whatever hardware-accelerated backend is on the machine. The 3 failing baselines were captured on the hardware path and were never regenerated for SwiftShader. that's the mismatch, not anything about the Rolldown/Playwright migration itself.

Ruled out a couple of alternatives before landing on that: (context: pixelmatch algo )

• Not simple AA/line-shift noise — ran the diffs through the clustering algo already in visualTest.js: significantDiffPixels came out at 160 and 257 against the 40px threshold, way past what tolerance-tuning could reasonably absorb.
• Not font-hinting — added --font-render-hinting=none --disable-lcd-text on top of the CI flags and reran under CI=true: diff numbers came back byte-identical, no change at all.
• Not font substitution — all 3 failing tests load the same bundled test/unit/assets/Inconsolata-Bold.ttf via loadFont(), not an OS-resolved font like 'monospace'/'serif', so it's the same font bytes locally and in CI either way.

Plan:
Firstly, I guess we should drop the process.env.CI ternary so the SwiftShader args always apply, local and CI alike keeps future baselines reproducible for every contributor instead of tied to one machine's renderer. And then we have to regenerate just the 3 affected typography screenshots under that path.

The screenshots should be regenerated because in order to incorporate the build updates, we either have to update the thresholds in the matching algo checkMatch which might some flase negatives in tests, or we can regenrate baselines to match CI's standard everywhere (these are only 3 tests).

cc @davepagurek